Conversation
|
@aboba Can we add this to the next interim's agenda please? |
|
@Orphis Yes. |
|
This issue was mentioned in WEBRTCWG-2024-05-21 (Page 22) |
71a2372 to
740b9cf
Compare
740b9cf to
1613039
Compare
1613039 to
1a211a1
Compare
| "title": "CloneArrayBuffer" | ||
| }, | ||
| "RTP-EXT-CAPTURE-TIME": { | ||
| "href": "http://www.webrtc.org/experiments/rtp-hdrext/abs-capture-time", |
There was a problem hiding this comment.
This normative reference redirects to a googlesource link. I'll need to check with folks internally how to handle this.
Can we add a note mentioning any efforts to standardize this?
My understanding is after an IETF effort it would end up here?
There was a problem hiding this comment.
See w3c/webrtc-extensions#216. I worry if we merge this it creates a blocker for advancement.
There was a problem hiding this comment.
We now have Harold’s draft (which will be up for adoption in IETF AVTCORE WG): https://datatracker.ietf.org/doc/draft-alvestrand-avtcore-abs-capture-time/
| sequence<unsigned long> contributingSources; | ||
| long long timestamp; // microseconds | ||
| unsigned long rtpTimestamp; | ||
| DOMHighResTimeStamp captureTimestamp; |
There was a problem hiding this comment.
Rename to captureTime for consistency with rVFC and others.
| "title": "CloneArrayBuffer" | ||
| }, | ||
| "RTP-EXT-CAPTURE-TIME": { | ||
| "href": "http://www.webrtc.org/experiments/rtp-hdrext/abs-capture-time", |
There was a problem hiding this comment.
| "href": "http://www.webrtc.org/experiments/rtp-hdrext/abs-capture-time", | |
| "href": "https://www.webrtc.org/experiments/rtp-hdrext/abs-capture-time", |
|
Editors can integrate pending the adoption of https://datatracker.ietf.org/doc/draft-alvestrand-avtcore-abs-capture-time/ |
7 participants
Fixes #225
Preview | Diff